Enabling perimeter-based user interactions with a user device

ABSTRACT

A user device may include a display that includes a first area and a second area. The first area may be located around a periphery of the second area, and the first area may include a touch-sensitive surface. The user device may detect a user interaction with the first area and may determine an action associated with the user interaction. The user device may perform the action in association with information displayed in the second area.

BACKGROUND

A touch screen is an input component that is normally layered on the topof an electronic visual display of a device. A user may provide input toand/or control the device through single and/or multi-touch gestures bytouching the touch screen with one or more fingers or a stylus. The usermay interact with the device by contacting the touch screen at locationscorresponding to user-interface objects.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for enablingperimeter-based user interactions with a user device;

FIG. 5 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4;

FIG. 6 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4; and

FIG. 7 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A wearable user device, such as a smart watch, may include atouch-sensitive display (e.g., a touch screen) that may be used todisplay screen information (e.g., user-interface objects and/orcontent), and provide a user interface via which a user may interactwith the user device. The user device may detect a user interaction(e.g., a touch gesture) with the touch-sensitive display at a particularposition and may perform an action corresponding to the user interaction(e.g., may update a display of screen information). However, in somecases, one or more of the user's fingers may occupy a majority of thetouch-sensitive display as the user interacts with the user device.Thus, the user may obfuscate the screen information while interactingwith the user device.

Implementations described herein may assist a user device in enablingperimeter-based user interactions, thereby allowing a user to manipulatescreen information without directly interacting with the screeninformation. Implementations described herein may assist a user inefficiently using the user device by reducing a quantity of operatingerrors associated with using the user device, thereby conservingprocessor and/or memory resources.

While implementations will be described in terms of a user device in theform of a smart watch, these implementations are not limited to smartwatches. In practice, these implementations may be used in conjunctionwith other types of user devices that have a touch-sensitive display,such as a smart phone, a tablet device, and other handheld user devices.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1, and by reference number 110, auser device may detect a user interaction with a perimeter areaassociated with the user device. For example, the user device (e.g., asmart watch) may include a touch-sensitive surface that includes aperimeter area and a display area. As shown, the user device may detecta touch gesture (e.g., a clockwise swipe) associated with the perimeterarea. For example, a user of the user device may establish a point ofcontact with the perimeter area at a first position (e.g., by touchingthe perimeter area), and may move the point of contact with theperimeter area in a clockwise direction to a second position.

As shown by reference number 120, the user device may determine anaction associated with the user interaction. For example, the userdevice may determine an action (e.g., a scroll) to be performed inassociation with screen information (e.g., user-interface objects, suchas icons) being displayed in association with the display area. The userdevice may determine the action based on mapping the user interaction tothe action. As further shown by reference number 120, the user devicemay perform the action in association with screen information beingprovided for display. For example, as shown, the user device may performa vertical scroll (e.g., may scroll through the user-interface objects)based on the user interaction with the perimeter area.

Implementations described herein may assist a user in navigating screeninformation by performing touch gestures in association with a perimeterarea of a user device. In this way, the screen information may remainvisible to the user as the user interacts with the user device.Implementations described herein may reduce a quantity of operatingerrors associated with using a user device, thereby conserving processorand/or memory resources of the user device.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user device 210, a server device 220,and a network 230. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

User device 210 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith a perimeter-based user interaction. For example, user device 210may include a communication and/or computing device, such as a wearablecommunication device (e.g., a smart wristwatch, an activity band, or apair of smart eyeglasses), a mobile phone (e.g., a smart phone or aradiotelephone, etc.), a laptop computer, a tablet computer, a handheldcomputer, a gaming device, or a similar type of device.

Server device 220 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith a perimeter-based user interaction. In some implementations, serverdevice 220 may include a communication interface that allows serverdevice 220 to receive information from and/or transmit information toother devices in environment 200. For example, server device 220 mayprovide, to user device 210, information that identifies a mapping of auser interaction to an action. Additionally, or alternatively, serverdevice 220 may provide information (e.g., a configuration file and/or asoft key map file) that enables user device 210 to detect and/ordetermine user interactions with a perimeter area of user device 210.

Network 230 may include one or more wired and/or wireless networks. Forexample, network 230 may include a cellular network (e.g., a long-termevolution (LTE) network, a third generation (3G) network, a codedivision multiple access (CDMA) network, etc.), a public land mobilenetwork (PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210 and/or server device 220. In someimplementations, user device 210 and/or server device 220 may includeone or more devices 300 and/or one or more components of device 300. Asshown in FIG. 3, device 300 may include a bus 310, a processor 320, amemory 330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a processor (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), and/or an accelerated processing unit (APU)), amicroprocessor, a microcontroller, and/or any processing component(e.g., a field-programmable gate array (FPGA) and/or anapplication-specific integrated circuit (ASIC)) that interprets and/orexecutes instructions. In some implementations, processor 320 includesone or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, one or more touch-sensitive surfaces, a keyboard, a keypad, amouse, a button, a switch, and/or a microphone). Additionally, oralternatively, input component 350 may include a sensor for sensinginformation (e.g., a global positioning system (GPS) component, anaccelerometer, a gyroscope, and/or an actuator). Output component 360includes a component that provides output information from device 300(e.g., a display, a speaker, and/or one or more light-emitting diodes(LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for enablingperimeter-based user interactions with a user device. In someimplementations, one or more process blocks of FIG. 4 may be performedby user device 210. In some implementations, one or more process blocksof FIG. 4 may be performed by another device or a group of devicesseparate from or including user device 210, such as server device 220.

As shown in FIG. 4, process 400 may include detecting a user interactionwith a perimeter area associated with a user device (block 410). Forexample, user device 210 may detect a user interaction (e.g., a touchgesture) with a perimeter area associated with user device 210. In someimplementations, user device 210 may include a touch-sensitive surfacethat includes both a perimeter area and a display area. Additionally, oralternatively, the display area (e.g., a touch screen) may providescreen information for display whereas the perimeter area may notprovide screen information for display. In some implementations, theperimeter area may be separate from the display area (e.g., theperimeter area and the display area may include separate surfaces).Alternatively, the perimeter area may be an extension of the displayarea. In some implementations, the perimeter area may partially orcompletely surround the display area. For example, the perimeter areaand the display area may form a planar surface where the perimeter areaforms a perimeter around the display area and/or is located around aperiphery of the display area. Alternatively, a surface of the perimeterarea may be perpendicular to a surface of the display area, in someimplementations.

In some implementations, the display area may display screeninformation. For example, screen information may include content, suchas video, images, and/or text. Additionally, or alternatively, screeninformation may include user-interface objects, such as icons, menus,lists, boxes, soft keys (e.g., “virtual keys”), and/or the like. In someimplementations, the screen information may be associated with aparticular screen (e.g., a home screen, a settings screen, and/or anapplication screen), a particular sequence of screens, and/or the like.In some implementations, the perimeter area may not display screeninformation. Additionally, or alternatively, the perimeter area maydisplay a subset of screen information and/or may include one or moreuser-interface objects (e.g., soft keys).

In some implementations, user device 210 may selectively display theperimeter area. For example, user device 210 may modify (e.g., reduce) asize of the display area based on detecting a user interaction (e.g.,may display the perimeter area and the display area via a display whenthe user interaction is detected). Additionally, user device 210 mayincrease the size of the display area based on detecting that the userinteraction has ended or that another user interaction has occurred(e.g., may display the display area and not the perimeter area via thedisplay such that the display area covers an entirety of the display).Additionally, or alternatively, user device 210 may selectively displaythe perimeter area based on an application that is presenting screeninformation in the display area. For example, user device 210 maydisplay the perimeter area for a particular application, which may allowthe user to interact with the perimeter area to manipulate screeninformation associated with the particular application. Additionally, oralternatively, user device 210 may not display the perimeter area foranother application that is presenting screen information in the displayarea (e.g., may display the display area and not the perimeter area).

In some implementations, the user interaction may include a touchgesture (e.g., a single touch gesture and/or a multi-touch gesture). Forexample, user device 210 may detect a single touch gesture based ondetecting a single point of contact (e.g., a press of a user's finger)with a touch-sensitive surface of user device 210, a movement associatedwith the point of contact, and/or a break (e.g., a lift of the user'sfinger) of the single point of contact. Additionally, or alternatively,user device 210 may detect a multi-touch gesture based on detectingmultiple points of contact with a touch-sensitive surface of user device210. In some implementations, a touch gesture may include a tap, adouble-tap, a tap and hold, a nudge, a pinch, a spread, a slide, a drag,a flick, or a swipe. The user may perform a touch gesture using anappendage (e.g., a finger) and/or an object (e.g., a stylus).

In some implementations, user device 210 may determine a parameterassociated with the user interaction. For example, user device 210 maydetermine a quantity of points of contact, a position associated with apoint of contact (e.g., a position of an initial point of contract,positions associated with a movement of the point of contact, and/or aposition of a break of the point of contact), a direction of the userinteraction, a speed of the user interaction, a velocity of the userinteraction, an acceleration of the user interaction, a duration of theuser interaction, and/or the like. In some implementations, user device210 may determine a position associated with a user interaction based oncoordinate values (e.g., associated with a coordinate system), and maydetermine a change in position based on a change in coordinate values.Additionally, or alternatively, user device 210 may determine a positionbased on an angular value (e.g., relative to a particular point or axisassociated with user device 210), and may determine a change in positionbased on an increment and/or decrement in the angular value. In someimplementations, user device 210 may perform an action based on a userinteraction, as described below. Additionally, or alternatively, userdevice 210 may perform an action based on a parameter associated with auser interaction satisfying a threshold.

In some implementations, user device 210 may determine that a userinteraction is associated with the perimeter area. For example, userdevice 210 may determine a position of an initial point of contactassociated with the user interaction, and may determine whether theposition is associated with the perimeter area or the display area(e.g., based on a configuration file or a soft key map file). In someimplementations, user device 210 may determine whether the userinteraction is associated with the perimeter area or the display areabased on a coordinate value (or values) of a touch position (orpositions). Additionally, user device 210 may determine and/or performdifferent actions associated with the user interaction based ondetermining whether the user interaction is associated the perimeterarea or the display area. In some implementations, user device 210 maydetermine an action associated with the user interaction (e.g., amapping of a user interaction to an action) based on determining thatthe user interaction is associated with the perimeter area. In this way,user device 210 may detect a user interaction with the perimeter areaand may determine an action associated with the user interaction, asdescribed below.

As further shown in FIG. 4, process 400 may include determining anaction associated with the user interaction (block 420). For example,user device 210 may determine an action that is to be performed inassociation with screen information being provided for display inassociation with the display area. In some implementations, user device210 may determine an action associated with the user interaction basedon mapping the user interaction with the perimeter area to an action tobe performed in association with screen information being provided fordisplay in association with the display area. For example, user device210 may store information (e.g., in a data structure) that identifies amapping of a user interaction to an action. In some implementations, anaction may include a scroll (e.g., a horizontal, vertical, or circularscroll operation), a selection, a zoom (e.g., a zoom-in operation), arotation, a drag, a fling, a pan, a tilt, an expansion, a collapse,and/or the like.

In some implementations, user device 210 may map a single touch gesture(e.g., associated with a single point of contact) to an action. Forexample, user device 210 may map a swipe (e.g., a horizontal swipe, avertical swipe, a counterclockwise swipe, or a clockwise swipe) to ascroll (e.g., a horizontal scroll, a vertical scroll, a clockwisescroll, or a counterclockwise scroll). Additionally, or alternatively,user device 210 may map a tap to a selection.

In some implementations, user device 210 may map a multi-touch gestureto an action. For example, user device 210 may map a first swipeassociated with a first point of contact and a second swipe associatedwith a second point of contact with a zoom. In some implementations, thefirst swipe may be associated with a first direction (e.g., clockwise),whereas the second swipe may be associated with a second direction(e.g., counterclockwise).

Additionally, or alternatively, user device 210 may map a multi-touchgesture associated with a first swipe and a second swipe to a rotation.For example, the first swipe and the second swipe may be associated witha same direction (e.g., counterclockwise or clockwise). Additionally, oralternatively, user device 210 may map a multi-touch gesture, where thefirst point of contact is associated with a swipe and the second pointof contact is associated with a tap and hold, with a rotation.

In some implementations, user device 210 may determine multiple actionsassociated with a user interaction. For example, user device 210 maydetermine that a user interaction (e.g., a swipe) is associated withmultiple actions (e.g., a scroll and/or a zoom). In someimplementations, user device 210 may determine an action associated withthe user interaction based on the screen information and/or based on anapplication associated with the screen information. Additionally, oralternatively, user device 210 may store information (e.g., in a datastructure) that identifies a mapping of a user interaction to an actionassociated with an application and/or screen information. Additionally,or alternatively, user device 210 may identify an application associatedwith the screen information and/or a type of screen information (e.g., alist, a menu, and/or a map), and may determine an action associated withthe user interaction based on the application and/or the type of screeninformation. For example, if the screen information is associated with aparticular application (e.g., a map application), then user device 210may determine that a particular user interaction (e.g., a swipe) isassociated with a particular action (e.g., a rotation). Alternatively,if the screen information is associated with a list of user-interfaceobjects, then user device 210 may determine that the same userinteraction (e.g., the swipe) is associated with a different action(e.g., a scroll).

Additionally, or alternatively, user device 210 may determine an actionassociated with the user interaction based on a screen (e.g., a homescreen, a settings screen, and/or a screen associated with anapplication). For example, user device 210 may determine a first actionassociated with a user interaction based on a first screen associatedwith an application, and may determine a second action associated withthe same user interaction based on a second screen associated with theapplication. In this way, user device 210 may perform one or moreactions in association with screen information based on the userinteraction and/or based on an application or a screen associated withthe screen information, as described below.

In some implementations, user device 210 may determine an actionassociated with the user interaction based on a configuration (e.g., auser-configuration). For example, user device 210 may receive input(e.g., from a user of user device 210) identifying an action to beperformed in association with a user interaction. In someimplementations, the configuration may map a user interaction to anaction to be performed in association with particular screeninformation, screen information associated with a particularapplication, screen information associated with a particular screen, orthe like.

In some implementations, user device 210 may receive informationidentifying a configuration (e.g., from server device 220).Additionally, or alternatively, user device 210 may provide information(e.g., an instruction, such as an executable file) to another device(e.g., server device 220 and/or another user device 210). For example,user device 210 may generate the information (e.g., the executable file)and may provide the information to another device. Additionally, theother device may execute the information, which may allow the otherdevice to identify and/or store a user configuration. In this way, userdevice 210 may provide, to another user device 210, information thatidentifies a configuration, thereby allowing the other user device 210to identify a configuration without the user having to re-configure theother user device 210. In this way, processor and/or memory resourcesmay be conserved.

As further shown in FIG. 4, process 400 may include performing theaction in association with screen information being provided for display(block 430). For example, user device 210 may perform an action inassociation with screen information being provided for display in thedisplay area. In some implementations, user device 210 may perform anaction in association with the screen information based on the userinteraction with the perimeter area.

In some implementations, user device 210 may perform the action based ona parameter, such as a velocity parameter, an acceleration parameter, aduration parameter, or the like, associated with the user interaction.For example, user device 210 may scroll through screen information(e.g., multiple user-interface objects, such as a list) at a particularrate based on a velocity and/or an acceleration associated with the userinteraction. In this way, a user may control the rate at which displayedscreen information is updated.

In some implementations, user device 210 may perform a particular actionbased on an application associated with user device 210 and/or based onthe screen information. For example, assume that user device 210determines that the user interaction (e.g., a swipe) is associated witha particular action (e.g., a zoom). Further, assume that an applicationassociated with the screen information is incapable of processing theuser interaction (e.g., the application is not configured to processperimeter-based user interactions). In such cases, user device 210 maydetermine another action (e.g., an action that is native to an operatingsystem associated with user device 210 and/or the application) and mayperform the other action (e.g., a scroll).

Additionally, or alternatively, user device 210 may determine multipleactions (e.g., a scroll and/or a zoom) associated with a userinteraction (e.g., a swipe), and may provide information (e.g., one ormore events) that identifies the user interaction and/or one or moreparameters associated with the user interaction to an applicationassociated with user device 210. In this way, an application associatedwith user device 210 may process a particular event and user device 210may perform a corresponding action based on the application processingthe event.

In some implementations, the action may be associated with a particularapplication. For example, an action may execute the application, closethe application, quit the application, select a feature associated withan application, adjust a setting associated with the application,navigate screen information associated with the application, navigatescreens associated with the application, or the like. Additionally, oralternatively, the action may include responding to (e.g., answering ordismissing) a notification (e.g., a voice call, a message (e.g., shortmessage service (SMS) message), or a prompt), causing another device(e.g., a connected device) to respond to a notification, locking userdevice 210, unlocking user device 210, and/or the like.

Implementations described herein may assist a user in navigating screeninformation being provided for display via a user device by performingperimeter-based user interactions. In this way, screen information mayremain visible to the user as the user interacts with the user device.Implementations described herein may reduce a quantity of operatingerrors associated with using a user device and may enable a user to usethe user device more efficiently, thereby conserving processor and/ormemory resources of the user device.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a diagram of an example implementation 500 relating to exampleprocess 400 shown in FIG. 4. FIG. 5 shows an example of enablingperimeter-based user interactions with a user device.

As shown in FIG. 5, user device 210 may scroll through screeninformation based on detecting a swipe. For example, as shown byreference number 510, a user may interact with (e.g., touch) theperimeter area of user device 210 at a first position to establish apoint of contact. As shown by reference number 520, the user may movethe point of contact in a clockwise direction to a second position(e.g., may perform a clockwise swipe). User device 210 may detect theuser interaction with the perimeter area and may determine an actionassociated with the user interaction.

As shown by reference number 530, user device 210 may scroll throughscreen information (e.g., user-interface objects, such as icons)associated with a display area of user device 210. For example, asshown, user device 210 may provide multiple user-interface objects(e.g., icons) for display in association with the display area.Additionally, assume that user device 210 may scroll through theuser-interface objects in a clockwise and/or counterclockwise manner.Further, as shown by reference number 540, assume that a particularuser-interface component is in a selected position. In someimplementations, a user may perform another user interaction (e.g., atap) with the perimeter area to select a user-interface object that isin the selected position (e.g., to open an application and/or navigateto a screen). In this way, a user may perform one or more userinteractions with the perimeter area of user device 210 to navigateand/or select screen information while leaving the display areaunencumbered.

As indicated above, FIG. 5 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 5.

FIG. 6 is a diagram of an example implementation 600 relating to exampleprocess 400 shown in FIG. 4. FIG. 6 shows an example of enablingperimeter-based user interactions with a user device.

As shown in FIG. 6, user device 210 may zoom in on screen informationbased on a swipe. For example, as shown by reference number 610, a usermay interact with the perimeter area of user device 210 at a firstposition to establish a point of contact. As shown by reference number620, the user may move the point of contact in a vertical direction andthen in a horizontal direction (e.g., to perform a clockwise swipe).User device 210 may detect the user interaction and may determine anaction associated with the user interaction.

As shown by reference number 630, user device 210 may zoom in on screeninformation (e.g., a map associated with a map application) beingdisplayed in association with the display area. In some implementations,a user may perform another user interaction (e.g., a swipe in acounterclockwise direction) to cause user device 210 to zoom out. Inthis way, a user may perform one or more user interactions with theperimeter area of user device 210 to manipulate screen information.

As indicated above, FIG. 6 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 6.

FIG. 7 is a diagram of an example implementation 700 relating to exampleprocess 400 shown in FIG. 4. FIG. 7 shows an example of enablingperimeter-based user interactions with a user device.

As shown in FIG. 7, user device 210 may rotate screen information basedon detecting multiple swipes. For example, as shown by reference number710, a user may interact with the perimeter area of user device 210 at afirst position to establish a first point of contact and at a secondposition to establish a second point of contact. As shown by referencenumber 720, the user may move the first point of contact in a verticaldirection to a third position, and may move the second point of contractin a horizontal direction to a fourth position. User device 210 maydetect the user interaction and may determine an action associated withthe user interaction.

As shown by reference number 730, user device 210 may rotate the screeninformation (e.g., a map associated with a map application). In thisway, a user may perform multiple touch gestures in association with theperimeter area of user device 210 to manipulate screen information beingprovided for display in associated with the display area.

As indicated above, FIG. 7 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 7.

Implementations described herein may assist a user device in enablingperimeter-based user interactions. In this way, a user may manipulatescreen information by performing touch gestures with a perimeter area ofthe user device, which may allow screen information to remain visible toa user as the user interacts with the user device. Implementationsdescribed herein may assist a user in using a user device in anefficient manner, thereby reducing operating errors and conservingprocessor and/or memory resources.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, etc. A userinterface may provide information for display. In some implementations,a user may interact with the information, such as by providing input viaan input component of a device that provides the user interface fordisplay. In some implementations, a user interface may be configurableby a device and/or a user (e.g., a user may change the size of the userinterface, information provided via the user interface, a position ofinformation provided via the user interface, etc.). Additionally, oralternatively, a user interface may be pre-configured to a standardconfiguration, a specific configuration based on a type of device onwhich the user interface is displayed, and/or a set of configurationsbased on capabilities and/or specifications associated with a device onwhich the user interface is displayed.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A user device, comprising: a display including afirst area and a second area, the first area being located around aperiphery of the second area, the first area including a touch-sensitivesurface; and one or more processors to: receive a configuration file;store mapping information that identifies a mapping of a userinteraction to an action associated with an application based on theconfiguration file, the user interaction associated with the first area,and the application associated with information, including one or moreicons, displayed in the second area, an icon, of the one or more icons,being used to open the application; detect the user interaction, theuser interaction associated with one or more coordinate values;determine that the user interaction is associated with the first areabased on the one or more coordinate values and the configuration file,the user interaction occurring in the first area and not directlyoccurring with the icon; determine the action associated with the userinteraction based on the mapping, the action to be performed inassociation with the information displayed in the second area; performthe action in association with the information displayed in the secondarea, the action including opening the application associated with theicon; determine whether the application is a particular application; andincrease a size of the second area to cover an entirety of the displayafter opening the application based on determining that the applicationis the particular application, the first area no longer being displayedon the user device.
 2. The user device of claim 1, where the one or moreprocessors, when detecting the user interaction with the first area, areto: detect a movement of a point of contact from a first positionassociated with the first area to a second position associated with thefirst area, the movement being associated with a clockwise orcounterclockwise direction; and where the one or more processors, arefurther to: perform a scroll operation of the information displayed inthe second area.
 3. The user device of claim 1, where the one or moreprocessors, when detecting the user interaction with the first area, areto: detect a movement of a point of contact from a first positionassociated with the first area to a second position associated with thefirst area, the movement being associated with a clockwise orcounterclockwise direction; and where the one or more processors, arefurther to: perform a zoom operation of the information displayed in thesecond area.
 4. The user device of claim 1, where the one or moreprocessors, when determining the action associated with the userinteraction, are to: determine a first action associated with the userinteraction; determine a second action associated with the userinteraction; and where the one or more processors, when performing theaction in association with the information displayed in the second area,are to: perform the first action based on a first information displayedin the second area; and perform the second action based on a secondinformation displayed in the second area.
 5. The user device of claim 1,where the user device is a wearable user device.
 6. The user device ofclaim 1, where the one or more processors, when detecting the userinteraction with the first area, are to: determine a parameterassociated with the user interaction; and where the one or moreprocessors, when performing the action in association with theinformation displayed in the second area, are to: perform the actionbased on the parameter.
 7. The user device of claim 1, where the userinteraction includes at least one of: a tap, a swipe, a nudge, a pinch,a spread, a slide, a drag, or a flick.
 8. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors of a user device, cause the one or more processors to:receive a configuration file; store mapping information that identifiesa mapping of a user interaction to an action associated with anapplication based on the configuration file, the user interactionassociated with a first area, and the application associated withinformation, including one or more icons, displayed in a second area, anicon, of the one or more icons, being used to open the application;detect the user interaction with a display of the user device, thedisplay including the first area and the second area, the first areabeing associated with a touch-sensitive surface, the first areasurrounding the second area, and the user interaction associated withone or more coordinate values; determine that the user interaction isassociated with the first area based on the one or more coordinatevalues and the configuration file, the user interaction occurring in thefirst area and not directly occurring with the icon; determine theaction associated with the user interaction based on the mappinginformation, the action to be performed in association with theinformation being displayed in the second area; perform the action inassociation with the information being displayed in the second area, theaction including opening the application associated with the icon;determine whether the application is a particular application; andincrease a size of the second area to cover an entirety of the displayafter opening the application based on determining that the applicationis the particular application, the first area no longer being displayedon the user device.
 9. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions, that cause the one or moreprocessors to receive the configuration file: receive auser-configuration that identifies the action associated with the userinteraction; and where the one or more instructions, that cause the oneor more processors to determine the action associated with the userinteraction, cause the one or more processors to: determine the actionbased on the user-configuration.
 10. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: generate information that includes the mapping ofthe user interaction to the action to permit the mapping to be sharedwith another device.
 11. The non-transitory computer-readable medium ofclaim 8, where the user device includes a smart watch.
 12. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions, when executed by the one or more processors, furthercause the one or more processors to: display the first area based ondetecting the user interaction.
 13. The non-transitory computer-readablemedium of claim 8, where the one or more instructions, that furthercause the one or more processors to: determine another action associatedwith the application when the application is incapable of processing theuser interaction, and perform the other action.
 14. The non-transitorycomputer-readable medium of claim 8, where the user interaction includesat least one of: a tap, a swipe, a nudge, a pinch, a spread, a slide, adrag, or a flick.
 15. A method, comprising: receiving, by a user device,a configuration file; storing, by the user device, mapping informationthat identifies a mapping of a user interaction to an action associatedwith an application based on the configuration file, the userinteraction associated with a first area associated with a display ofthe user device, and the application associated with information,including one or more icons, displayed in a second area associated withthe display of the user device, an icon, of the one or more icons, beingused to open the application; detecting, by the user device, the userinteraction associated with the display of the user device, the displayincluding the first area and the second area, the first area including atouch-sensitive surface, the first area being located around a peripheryof the second area, and the user interaction associated with one or morecoordinates; determining, by the user device, that the user interactionis associated with the first area based on the one or more coordinatesand the configuration file, the user interaction occurring in the firstarea and not directly occurring with the icon; determining, by the userdevice, the action associated with the user interaction based on themapping, the action to be performed in association with the informationdisplayed in the second area; performing, by the user device, the actionin association with the information displayed in the second area, theaction including opening the application associated with the icon;determining, by the user device, whether the application is a particularapplication; and increasing, by the user device, a size of the secondarea to cover an entirety of the display after opening the applicationbased on determining that the application is the particular application,the first area no longer being displayed on the user device.
 16. Themethod of claim 15, where determining the action associated with theuser interaction comprises: determining the action associated with theuser interaction based on a screen associated with the informationdisplayed in the second area.
 17. The method of claim 15, furthercomprising: determining that a parameter associated with the userinteraction satisfies a threshold; and performing the action based onthe parameter satisfying the threshold.
 18. The method of claim 15,further comprising: determining another action associated with theapplication when the application is incapable of processing the userinteraction, and performing the other action.
 19. The method of claim15, further comprising: provide information provided in theconfiguration file to another device, the information being used toidentify a configuration without the other device needing to bereconfigured by a user.
 20. The method of claim 15, further comprising:generating an executable file that includes the mapping of the userinteraction to the action to permit the mapping to be shared withanother device.